home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Gold Medal Software 3
/
Gold Medal Software - Volume 3 (Gold Medal) (1994).iso
/
bbsutils
/
accnet42.arj
/
ACCESSNT.GDE
< prev
next >
Wrap
Text File
|
1994-03-07
|
9KB
|
201 lines
──────────────────────────────────────────────────────────────────────
──────────────────────────────────────────────────────────────────────
╓─╖ ╓──┐ ╓──┐ ╓─── ╓──┐ ╓──┐ ╓┐ ╥ ╓─── ──╥──
╓╨─╨╖ ║ ║ ╟── ╙──╖ ╙──╖ ║└┐║ ╟── ║
╨ ╨ ╙──┘ ╙──┘ ╙─── └──╜ └──╜ ╨ └╜ ╙─── ╨ (TM)
I n t e r n a t i o n a l N e t - M a i l N e t w o r k
──────────────────────────────────────────────────────────────────────
──────────────────────────────────────────────────────────────────────
╓─── . ╥ ╓ .
║ ╓╖ ╖ ╖ ╥ ╓─╢ ╓─╖ ║ ╥ ╖─╖ ╓─╖ ╓──
╙──╜ ╙─╨ ╜ ╙─╨ ╙── ╨ ╜ ╜ ╜ ╙── ──╜
Preface:
We consider AccessNet to be the friendliest netmail network around! In order
to maintain our friendly and helpful atmosphere, it is necessary to have some
rules or guidelines. These guidelines are meant to be just that - guidelines.
This is too friendly a network for major quibbling. <smile>
┌┬───────────────────────┬┐
││ Mandatory Conferences ││
└┴───────────────────────┴┘
■ All of the AccessNet "core" conferences must be carried by ALL
participating Nodes.
■ There are two RoseNet conferences (see ACCESSNT.LST) that are
mandatory: The RoseMail and RoseReader support conferences. Please
note that only those using RoseMail to transfer their mail are
required to carry the two.
┌┬───────────────────┬┐
││ Mandatory Reading ││
└┴───────────────────┴┘
■ All AccessNet SysOps are required to read the AccessNet Administration
conference.
┌┬───────────────────┬┐
││ Posting Etiquette ││
└┴───────────────────┴┘
■ All AccessNet SysOps are strongly encouraged to enforce proper
'quoting' of messages. Quoting of entire messages is not only
sloppy, but is a burden to those who are paying the phone bill.
■ When replying to messages - People should strongly consider the
TOPIC of their reply. Too many netmail networks (including this one
at times) have lengthy message threads that do not have any actual
continuity.
■ When posting a new message - People should consider the MOST
appropriate conference for the topic of their discussion. When
people enter messages in the wrong conference it causes misplaced
threads. Not everyone has every conference in their message queue.
As a result a user who may want to read a message about modems, for
example, may never read that ONE all important message because it
was entered in a wrong conference. This should be avoided at all
times.
■ BBS ads should not exceed one per week for any bulletin board. BBS
ads belong in the BBS conference.
┌┬──────────────────┬┐
││ Conference Hosts ││
└┴──────────────────┴┘
Job Description:
Conference Hosts are required to monitor their conference on a
daily basis. They are also required to generate messages within
their conference in an attempt to promote quality activity.
Conferences Hosts are expected to report any messages of poor
taste, poor etiquette, or problems to the SysOp of the offending
board via the AccessNet Administration Conference. The SysOp of
the offending board will then be responsible for handling the
situation.
Host Guidelines:
■ Conference Hosts should have a good working knowledge of English
grammar and spelling. (This is important so that their messages
are not just "seen", they are read and understood.)
■ Conference Hosts must understand and utilize proper message
etiquette (i.e. quoting and "mood punctuation.") Since their
messages will be setting the tone and atmosphere of the
conversation, their messages should be friendly and informative.
■ Conference Hosts are strongly encouraged to use an off-line mail
reader for their messages. Using an offline mail reader will
enable such features as: spell checking, reduction in online time,
and the ability to maintain a database of messages.
■ Conference Hosts are expected to Have fun! If the Host isn't
having fun, chances are the others aren't either. <smile> :)
┌┬───────────────────────────────────────────────────────────────────┬┐
││ Alias's are permitted in AccessNet under the following guidelines:││
└┴───────────────────────────────────────────────────────────────────┴┘
■ It is AccessNet's understanding that each Node SysOp is responsible
for the names used on his/her own BBS.
┌┬───────────┬┐
││ Tag Lines ││
└┴───────────┴┘
■ There Should not be more than 3 tag lines within any message (one of
these tag lines must be the required AccessNet Node tag line).
Tasteless tag lines are discouraged. More than 3 tag lines is
considered discourteous to those Node SysOps having to transfer mail
long distance.
■ ALL Nodes & Hubs must have the proper AccessNet tagline setup in
their respective software. All taglines must also have the City &
State and or country included.
Examples:
PostLink: NET-TAG-LINE=<<<<< AccessNet >>>>>
RoseMail: AccessNet ▌Your BBS Name, City, State here
^^ Space Alt-221
┌┬────────────┬┐
││ Signatures ││
└┴────────────┴┘
■ There should not be more than 2 lines relating to one's signature...
See "Tag Lines" above.
┌┬─────────────────────────────────┬┐
││ No offensive or abusive language││
└┴─────────────────────────────────┴┘
■ Keep it clean.
┌┬────────────────────────┬┐
││ Transferring Frequency ││
└┴────────────────────────┴┘
■ All Nodes must transfer mail at least once per day. By transferring
your mail each day, your users will benefit from the increased
response they will gain. It is imperative that ALL SysOps in
AccessNet understand that the quality of our network is based on
how often mail is transferred. When a Node does not transfer
often, users tend to become discouraged with the message base. It
is understood that Murphy's law effects ALL SysOps - when there is a
problem, it is the responsibility of the Node SysOp to contact their
supporting Hub.
┌┬───────────────────┬┐
││ Internet / UseNet ││
└┴───────────────────┴┘
■ Those picking up UseNet newsgroups are required to pay their Hub
every six months (in advance) for the service. See USENET.$$$ for
billing information.
┌┬──────────────────────┬┐
││ HUB Responsibilities ││
└┴──────────────────────┴┘
■ Hub SysOps are responsible for ensuring that their Nodes follow our
guidelines.
┌┬────────────────────┬┐
││ Vacationing SysOps ││
└┴────────────────────┴┘
■ It is understood that SysOps take vacations. AccessNet requests
that a vacationing SysOp delegate to another responsible SysOp the
ability to monitor the BBS in his/her absence. In the event that a
Node does not transfer mail within 3 consecutive days, the Hub SysOp
may decline to hold mail until the Node SysOp has contacted him/her.
It is also understood that callers may commit 'violations' of
AccessNet's guidelines in the absence of a full time SysOp and that
immediate action may not be able to be taken by the appointed SysOp.
┌┬──────────────────────────────┬┐
││ Do you want to become a Hub? ││
└┴──────────────────────────────┴┘
■ In order to become an AccessNet Hub, you must have been transferring
mail for at least Six months with our network. Contact the Nav Team
for network for more details.
──────────────────────────────────────────────────────────────────────
┌────────────┐
┌──┤ DISCLAIMER ├─────────────────────────────────────────────────────────┐
│ └────────────┘ Neither AccessNet, The ACCESS Network, or any related │
│ component to either is responsible for anything. All AccessNet SysOps │
│ are responsible for following local laws in regards to not allowing │
│ minors access to the adult conferences! By applying to AccessNet you │
│ are in agreement that acceptance or rejection of your application will │
│ be at the sole discretion of the AccessNet Administrators. If your │
│ application is accepted, you will be welcomed as a 'trial' member for │
│ six months. It is understood that AccessNet Administrators reserve the │
│ right to allow, disallow, include, or remove any active or non-active │
│ Node or applicant at anytime time and without any notice. By becoming │
│ an AccessNet SysOp or applicant, you are agreeing to these terms. │
└─────────────────────────────────────────────────────────────────────────┘